Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dfde9a6cd6a9033ce4bd20abe4f18e4dae6cd2140f88b3e30239c04a1a3247b

Tx prefix hash: 1c18260ed175aa9db3665765e2e49aeeef7bb4d0affb0fe603f2d9f1785e042a
Tx public key: 8f49babe61fe2380ac3066be96ac20aad42f4cd582a0b3042b0f11ec1fe14a21
Timestamp: 1712921694 Timestamp [UCT]: 2024-04-12 11:34:54 Age [y:d:h:m:s]: 00:320:13:00:49
Block: 998851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229150 RingCT/type: yes/0
Extra: 018f49babe61fe2380ac3066be96ac20aad42f4cd582a0b3042b0f11ec1fe14a2102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d762257841a78f4dff9164d271d6a23546c7d3fca6d2344de4ea5c4067f13f6 0.600000000000 1459317 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": 998861, "vin": [ { "gen": { "height": 998851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d762257841a78f4dff9164d271d6a23546c7d3fca6d2344de4ea5c4067f13f6" } } ], "extra": [ 1, 143, 73, 186, 190, 97, 254, 35, 128, 172, 48, 102, 190, 150, 172, 32, 170, 212, 47, 76, 213, 130, 160, 179, 4, 43, 15, 17, 236, 31, 225, 74, 33, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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