Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af326df7cdb3b6b61fea2159dc59c2e544f5554c7bd32ca4d4da41c38005319d

Tx prefix hash: 5fad9142246b9ca65e2ad09a33b79bbef20aec1773c426c00edaae67b91b452d
Tx public key: 412e8996502793e70cd6419d1182da3542eed07e7ddb87d4de120bbc91e38d6e
Timestamp: 1581915810 Timestamp [UCT]: 2020-02-17 05:03:30 Age [y:d:h:m:s]: 04:323:06:45:32
Block: 66519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123484 RingCT/type: yes/0
Extra: 01412e8996502793e70cd6419d1182da3542eed07e7ddb87d4de120bbc91e38d6e021100000002c9f743ef000000000000000000

1 output(s) for total of 369.496865133000 dcy

stealth address amount amount idx
00: f83dc8b6134be00686a75b9a256836449254c7f20e7dd958a17f7266ac13b00d 369.496865133000 122534 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": 66529, "vin": [ { "gen": { "height": 66519 } } ], "vout": [ { "amount": 369496865133, "target": { "key": "f83dc8b6134be00686a75b9a256836449254c7f20e7dd958a17f7266ac13b00d" } } ], "extra": [ 1, 65, 46, 137, 150, 80, 39, 147, 231, 12, 214, 65, 157, 17, 130, 218, 53, 66, 238, 208, 126, 125, 219, 135, 212, 222, 18, 11, 188, 145, 227, 141, 110, 2, 17, 0, 0, 0, 2, 201, 247, 67, 239, 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