Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c25030f2999349d9d7871deee45429c1773b4f2b52b650475dc4d1f6e6e7b23a

Tx prefix hash: 813a2b11e9eb2a0a1a38f358be79f5cd0bcfef84117583487602d61ad0193e51
Tx public key: 8a27c8c3a6b14a2dd7c8f84f745c134edc6a2cfa9569b7cfc6468904ee081971
Timestamp: 1734464537 Timestamp [UCT]: 2024-12-17 19:42:17 Age [y:d:h:m:s]: 00:018:10:26:20
Block: 1177382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13170 RingCT/type: yes/0
Extra: 018a27c8c3a6b14a2dd7c8f84f745c134edc6a2cfa9569b7cfc6468904ee0819710211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f7f8b967137225d6768d88bf4355493b3cbb355bcf7b37695beebfdbfcdd5b9 0.600000000000 1663753 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": 1177392, "vin": [ { "gen": { "height": 1177382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f7f8b967137225d6768d88bf4355493b3cbb355bcf7b37695beebfdbfcdd5b9" } } ], "extra": [ 1, 138, 39, 200, 195, 166, 177, 74, 45, 215, 200, 248, 79, 116, 92, 19, 78, 220, 106, 44, 250, 149, 105, 183, 207, 198, 70, 137, 4, 238, 8, 25, 113, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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