Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3deeb5d4a96805c666d9e3cfc723d7b6ff1cb6b0018d31453e34511826ed4b4

Tx prefix hash: bc703477fb5a70a2723974bd75754f7caf00904272f894774f0e3d5d0daa6f6a
Tx public key: d1b1e5606c55e4a7655d353931fdf7e8f4a5b81a3ac23b5c8fb28f299e92cd7a
Timestamp: 1756053966 Timestamp [UCT]: 2025-08-24 16:46:06 Age [y:d:h:m:s]: 00:093:21:19:33
Block: 1353536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67046 RingCT/type: yes/0
Extra: 01d1b1e5606c55e4a7655d353931fdf7e8f4a5b81a3ac23b5c8fb28f299e92cd7a0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e47936c2a20a5fa409eeefbef7b867ce794ef8880b79a25f4834182e4684de8d 0.600000000000 1841511 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": 1353546, "vin": [ { "gen": { "height": 1353536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e47936c2a20a5fa409eeefbef7b867ce794ef8880b79a25f4834182e4684de8d" } } ], "extra": [ 1, 209, 177, 229, 96, 108, 85, 228, 167, 101, 93, 53, 57, 49, 253, 247, 232, 244, 165, 184, 26, 58, 194, 59, 92, 143, 178, 143, 41, 158, 146, 205, 122, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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