Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15049889609fa770b06546d58b3030da9a1fd13bb4c7c694f76bbf43a5c48bb2

Tx prefix hash: 571e5eedd3fdf6d93d61bb19c71d3302694b6897740758ff406d5f60582e1442
Tx public key: d07a434724b854227df802cfdfec2ded41865e807f837df13167e718d16c1d4d
Timestamp: 1581799708 Timestamp [UCT]: 2020-02-15 20:48:28 Age [y:d:h:m:s]: 05:262:08:05:55
Block: 65570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1338262 RingCT/type: yes/0
Extra: 01d07a434724b854227df802cfdfec2ded41865e807f837df13167e718d16c1d4d02110000001d4ac5aa02000000000000000000

1 output(s) for total of 372.175417351000 dcy

stealth address amount amount idx
00: 656a826eb0cf9564481fd2c5cbcce2234a9abb0eaa6d2acf8023eb637fef7a62 372.175417351000 120997 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": 65580, "vin": [ { "gen": { "height": 65570 } } ], "vout": [ { "amount": 372175417351, "target": { "key": "656a826eb0cf9564481fd2c5cbcce2234a9abb0eaa6d2acf8023eb637fef7a62" } } ], "extra": [ 1, 208, 122, 67, 71, 36, 184, 84, 34, 125, 248, 2, 207, 223, 236, 45, 237, 65, 134, 94, 128, 127, 131, 125, 241, 49, 103, 231, 24, 209, 108, 29, 77, 2, 17, 0, 0, 0, 29, 74, 197, 170, 2, 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