Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ffd0aef946c46f448752c050a1cb38d265b33d045cb64e435fd63a74526e26b

Tx prefix hash: c1ebffa8bace8bf4ba3bb4b650d72f4534cb03a6df87fcd019be87282ff54141
Tx public key: 7e82e88bb97794d195477b33cf4d66c130603350003e0a206859f06a8c2e7d10
Timestamp: 1593017635 Timestamp [UCT]: 2020-06-24 16:53:55 Age [y:d:h:m:s]: 04:320:05:11:33
Block: 110462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168982 RingCT/type: yes/0
Extra: 017e82e88bb97794d195477b33cf4d66c130603350003e0a206859f06a8c2e7d1002110000001446a11e8a000000000000000000

1 output(s) for total of 264.237399393000 dcy

stealth address amount amount idx
00: 0b38aeb9a9d14ddd7b35af1dca97f1dc9395b85017441af602eca82a1a48eb93 264.237399393000 191346 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": 110472, "vin": [ { "gen": { "height": 110462 } } ], "vout": [ { "amount": 264237399393, "target": { "key": "0b38aeb9a9d14ddd7b35af1dca97f1dc9395b85017441af602eca82a1a48eb93" } } ], "extra": [ 1, 126, 130, 232, 139, 185, 119, 148, 209, 149, 71, 123, 51, 207, 77, 102, 193, 48, 96, 51, 80, 0, 62, 10, 32, 104, 89, 240, 106, 140, 46, 125, 16, 2, 17, 0, 0, 0, 20, 70, 161, 30, 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