Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ce7140b971a40ae031434bbeb92fe2d1e5b0d007664a288bef566ca2225344

Tx prefix hash: 036d4a05306531dfd96d3939bb004ebd1ce89a06b824f339a145b88733383db1
Tx public key: 64a9fd52a81482d14cb3521772033c2fbde90b71deb93616cae2bf38cb0bc08b
Timestamp: 1582130854 Timestamp [UCT]: 2020-02-19 16:47:34 Age [y:d:h:m:s]: 04:323:04:10:34
Block: 68376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123325 RingCT/type: yes/0
Extra: 0164a9fd52a81482d14cb3521772033c2fbde90b71deb93616cae2bf38cb0bc08b02110000000103d36d11000000000000000000

1 output(s) for total of 364.286212039000 dcy

stealth address amount amount idx
00: 4892534da5e11f9bf964653d73238fde98bbfec4d9341ee91c9e20a03f89fb7c 364.286212039000 125958 of 0

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": 68386, "vin": [ { "gen": { "height": 68376 } } ], "vout": [ { "amount": 364286212039, "target": { "key": "4892534da5e11f9bf964653d73238fde98bbfec4d9341ee91c9e20a03f89fb7c" } } ], "extra": [ 1, 100, 169, 253, 82, 168, 20, 130, 209, 76, 179, 82, 23, 114, 3, 60, 47, 189, 233, 11, 113, 222, 185, 54, 22, 202, 226, 191, 56, 203, 11, 192, 139, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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