Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be20c398269a5e75c4c16246191d6adbd20d92a697e0084c64ce3bfe17e367e

Tx prefix hash: f00c5a58721274c4e27e7dd1f6396f5f747456f22e32f3bf911144b52ebc2cc0
Tx public key: 244030c3446cfc269fa344deee5b5dd27adffd04b1bc1fcf086dd1ae84f858ab
Timestamp: 1635335428 Timestamp [UCT]: 2021-10-27 11:50:28 Age [y:d:h:m:s]: 03:060:08:13:21
Block: 361542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 821555 RingCT/type: yes/0
Extra: 01244030c3446cfc269fa344deee5b5dd27adffd04b1bc1fcf086dd1ae84f858ab0211000000011154028c000000000000000000

1 output(s) for total of 38.910040017000 dcy

stealth address amount amount idx
00: 9f0834cb21b9b1d778e31754e344dc2773ff2e8f0c1d7484430f279ce782dcd2 38.910040017000 735512 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": 361552, "vin": [ { "gen": { "height": 361542 } } ], "vout": [ { "amount": 38910040017, "target": { "key": "9f0834cb21b9b1d778e31754e344dc2773ff2e8f0c1d7484430f279ce782dcd2" } } ], "extra": [ 1, 36, 64, 48, 195, 68, 108, 252, 38, 159, 163, 68, 222, 238, 91, 93, 210, 122, 223, 253, 4, 177, 188, 31, 207, 8, 109, 209, 174, 132, 248, 88, 171, 2, 17, 0, 0, 0, 1, 17, 84, 2, 140, 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