Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc2b0f0eef3e2ee94fbded3ddde33888f24f7177bf7a45fdffe66e1fed4d0f8

Tx prefix hash: bd90eb7cab768e37ad1ea21d281ef9f463424756c7e5678bffd209ff6e5d75fc
Tx public key: 0d5d5bbdd2eec663379bede7b10a1bd2eec83903e2cbf29ab9ff6142c7f92e38
Timestamp: 1741703937 Timestamp [UCT]: 2025-03-11 14:38:57 Age [y:d:h:m:s]: 00:254:23:20:18
Block: 1237036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179954 RingCT/type: yes/0
Extra: 010d5d5bbdd2eec663379bede7b10a1bd2eec83903e2cbf29ab9ff6142c7f92e38021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61064a5fdf60eea42fa3ff8141c97c31b02fd833d70e4fdccd4e9822949ed6f4 0.600000000000 1723991 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": 1237046, "vin": [ { "gen": { "height": 1237036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61064a5fdf60eea42fa3ff8141c97c31b02fd833d70e4fdccd4e9822949ed6f4" } } ], "extra": [ 1, 13, 93, 91, 189, 210, 238, 198, 99, 55, 155, 237, 231, 177, 10, 27, 210, 238, 200, 57, 3, 226, 203, 242, 154, 185, 255, 97, 66, 199, 249, 46, 56, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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