Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe99bf1431695fb688a2c1c1b9a4c99bd6bb9bb7978720ad02f6f8d1ed2f479

Tx prefix hash: e7ff24c03a1813913003ba41f5aa716595f7e750814fb095443e6abcd52c58bb
Tx public key: 0e14b296a047dc3adea9d3421698ee9363657f5606b2aa38e3c196d4b7b1c51c
Timestamp: 1711977554 Timestamp [UCT]: 2024-04-01 13:19:14 Age [y:d:h:m:s]: 01:057:08:01:14
Block: 991014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302009 RingCT/type: yes/0
Extra: 010e14b296a047dc3adea9d3421698ee9363657f5606b2aa38e3c196d4b7b1c51c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cce9b42c3a5f2eb2118f8326bcfda3ef7769d41ec284131fa90de434712314da 0.600000000000 1451346 of 15

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": 991024, "vin": [ { "gen": { "height": 991014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cce9b42c3a5f2eb2118f8326bcfda3ef7769d41ec284131fa90de434712314da" } } ], "extra": [ 1, 14, 20, 178, 150, 160, 71, 220, 58, 222, 169, 211, 66, 22, 152, 238, 147, 99, 101, 127, 86, 6, 178, 170, 56, 227, 193, 150, 212, 183, 177, 197, 28, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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