Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018fd77880ebd3ae7beae689cdb4467aec3bea868c609b4fe4bd1ee093ba3cf6

Tx prefix hash: 2bcce303d9beaaa539516c6fa60785b38c4ec2d3a20c5926d54d6a8ee85785aa
Tx public key: 390505152880b9ee603107a394318fc628813d6dd73464d0ca77ecc961f1e086
Timestamp: 1592413859 Timestamp [UCT]: 2020-06-17 17:10:59 Age [y:d:h:m:s]: 05:137:03:39:51
Block: 109387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1292790 RingCT/type: yes/0
Extra: 01390505152880b9ee603107a394318fc628813d6dd73464d0ca77ecc961f1e0860211000000028a2ee0d9000000000000000000

1 output(s) for total of 266.413488424000 dcy

stealth address amount amount idx
00: 113e2d704d55d35b74e24e6c1ab6faab0639c2f3e041e02ce5f70802f9324db4 266.413488424000 189705 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": 109397, "vin": [ { "gen": { "height": 109387 } } ], "vout": [ { "amount": 266413488424, "target": { "key": "113e2d704d55d35b74e24e6c1ab6faab0639c2f3e041e02ce5f70802f9324db4" } } ], "extra": [ 1, 57, 5, 5, 21, 40, 128, 185, 238, 96, 49, 7, 163, 148, 49, 143, 198, 40, 129, 61, 109, 215, 52, 100, 208, 202, 119, 236, 201, 97, 241, 224, 134, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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