Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13b010fb2e182f626c3b5617d309a2ba664bb930d092e51ce6add1cbc649a26e

Tx prefix hash: e1578c6e3cbdfbc7f3ff2f55625c9e2f0aaf43d1aa73921ce5a7ebc8c89e321e
Tx public key: dedca7e3fa0aaf318496eaae2ec6a7363e3639cf1042913089cedb66d8bdd12a
Timestamp: 1621657930 Timestamp [UCT]: 2021-05-22 04:32:10 Age [y:d:h:m:s]: 03:357:08:33:16
Block: 264870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1017165 RingCT/type: yes/0
Extra: 01dedca7e3fa0aaf318496eaae2ec6a7363e3639cf1042913089cedb66d8bdd12a02110000001ffdc4fdba000000000000000000

1 output(s) for total of 81.353506847000 dcy

stealth address amount amount idx
00: b883fbd9f1be2792dacb14db411ddcef5158579df15da2cf4bc2c4c214e15f70 81.353506847000 556858 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": 264880, "vin": [ { "gen": { "height": 264870 } } ], "vout": [ { "amount": 81353506847, "target": { "key": "b883fbd9f1be2792dacb14db411ddcef5158579df15da2cf4bc2c4c214e15f70" } } ], "extra": [ 1, 222, 220, 167, 227, 250, 10, 175, 49, 132, 150, 234, 174, 46, 198, 167, 54, 62, 54, 57, 207, 16, 66, 145, 48, 137, 206, 219, 102, 216, 189, 209, 42, 2, 17, 0, 0, 0, 31, 253, 196, 253, 186, 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