Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e01091aeaab3de45448c38698c02f3da9480b20d34cacd04e140e7f5cd075417

Tx prefix hash: 661948a42d4ebf6803bc7245d48f3d898ec32d85fc4843aa4d805fce3b25f827
Tx public key: 2ea1354df60af93f143c6f856a7c09c17643192e06798202d6f36faf1f058c00
Timestamp: 1577907154 Timestamp [UCT]: 2020-01-01 19:32:34 Age [y:d:h:m:s]: 05:325:10:26:29
Block: 36560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1380183 RingCT/type: yes/0
Extra: 012ea1354df60af93f143c6f856a7c09c17643192e06798202d6f36faf1f058c00021100000020d81c26c0000000000000000000

1 output(s) for total of 464.368119120000 dcy

stealth address amount amount idx
00: a1c6bf1673ad6083fd729af43df6dee5cb15b8007fd35425cc8161db3a3ac48b 464.368119120000 61957 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": 36570, "vin": [ { "gen": { "height": 36560 } } ], "vout": [ { "amount": 464368119120, "target": { "key": "a1c6bf1673ad6083fd729af43df6dee5cb15b8007fd35425cc8161db3a3ac48b" } } ], "extra": [ 1, 46, 161, 53, 77, 246, 10, 249, 63, 20, 60, 111, 133, 106, 124, 9, 193, 118, 67, 25, 46, 6, 121, 130, 2, 214, 243, 111, 175, 31, 5, 140, 0, 2, 17, 0, 0, 0, 32, 216, 28, 38, 192, 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