Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b0c1c0b2c32a36f18598f484bbdfe6de44277865a7fa2e24b3b6d18ec141333b

Tx prefix hash: 9ef58b058a1695ddf329322afcb65a175c847a1f4f80ca94ef2df0d08ef9ae29
Tx public key: e17a6f66ae924f7b9b6744337749cc61bcef427922f603ca93181e0f80e8869e
Timestamp: 1743543255 Timestamp [UCT]: 2025-04-01 21:34:15 Age [y:d:h:m:s]: 00:233:02:50:40
Block: 1252236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164346 RingCT/type: yes/0
Extra: 01e17a6f66ae924f7b9b6744337749cc61bcef427922f603ca93181e0f80e8869e0211000000014060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ddc0adf7cfb3351260e1bd3e42d21fd7ef6883e1403e0c52770e01371bb9436 0.600000000000 1739315 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1252246, "vin": [ { "gen": { "height": 1252236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ddc0adf7cfb3351260e1bd3e42d21fd7ef6883e1403e0c52770e01371bb9436" } } ], "extra": [ 1, 225, 122, 111, 102, 174, 146, 79, 123, 155, 103, 68, 51, 119, 73, 204, 97, 188, 239, 66, 121, 34, 246, 3, 202, 147, 24, 30, 15, 128, 232, 134, 158, 2, 17, 0, 0, 0, 1, 64, 96, 246, 210, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8