Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebff80be780177614192e6bfd28ce29c44a033bfbef2d66edbd9969cda30e7a0

Tx prefix hash: 0a36a522da41c1ca42372a625a9401f400b543b4461bcce4e6cb8a3b7c114bbe
Tx public key: 788260ff42ff676024e4f552647084f2661d4985df092412bc1f6cdb570f1bf6
Timestamp: 1636797031 Timestamp [UCT]: 2021-11-13 09:50:31 Age [y:d:h:m:s]: 03:121:20:54:43
Block: 373428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 865521 RingCT/type: yes/0
Extra: 01788260ff42ff676024e4f552647084f2661d4985df092412bc1f6cdb570f1bf60211000000024a0f5013000000000000000000

1 output(s) for total of 35.536807351000 dcy

stealth address amount amount idx
00: 517690d9b613e56e60c36b8d512757aa80dd5cccea6a1e0748aa92f0a0700b13 35.536807351000 756166 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": 373438, "vin": [ { "gen": { "height": 373428 } } ], "vout": [ { "amount": 35536807351, "target": { "key": "517690d9b613e56e60c36b8d512757aa80dd5cccea6a1e0748aa92f0a0700b13" } } ], "extra": [ 1, 120, 130, 96, 255, 66, 255, 103, 96, 36, 228, 245, 82, 100, 112, 132, 242, 102, 29, 73, 133, 223, 9, 36, 18, 188, 31, 108, 219, 87, 15, 27, 246, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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