Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53699bf9bbe7899ccd064ecfe6a1bf4c8ef7ae107b6d9f4e471df8b7d3437f19

Tx prefix hash: 822ab50e05da8c6c3deed1f80e7c5513f590932758069542958f3fdef121d111
Tx public key: 204736e236172a4972627fd752115c53d8d1472d55eeeb0d7dae4fc0dc27964f
Timestamp: 1729035537 Timestamp [UCT]: 2024-10-15 23:38:57 Age [y:d:h:m:s]: 00:159:18:51:42
Block: 1132483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113949 RingCT/type: yes/0
Extra: 01204736e236172a4972627fd752115c53d8d1472d55eeeb0d7dae4fc0dc27964f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e042e8148b76fe7b1d6309279152cfd3c1c2d714d9940a0f1a39b05fedbd02b 0.600000000000 1615398 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": 1132493, "vin": [ { "gen": { "height": 1132483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e042e8148b76fe7b1d6309279152cfd3c1c2d714d9940a0f1a39b05fedbd02b" } } ], "extra": [ 1, 32, 71, 54, 226, 54, 23, 42, 73, 114, 98, 127, 215, 82, 17, 92, 83, 216, 209, 71, 45, 85, 238, 235, 13, 125, 174, 79, 192, 220, 39, 150, 79, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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