Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88195f97c940f89deedeecd5329c9c53fb36db61a418a30891f0763fa5c568ad

Tx prefix hash: 63c938eb71871d8d13267e662309a1c843598f7611623f29c0215114a7cba8ba
Tx public key: 22fe4993025b6d66d61071003472a6f55d20c6e7a1b8e522a036e38bcf1318cc
Timestamp: 1718368605 Timestamp [UCT]: 2024-06-14 12:36:45 Age [y:d:h:m:s]: 00:258:17:32:31
Block: 1044041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184855 RingCT/type: yes/0
Extra: 0122fe4993025b6d66d61071003472a6f55d20c6e7a1b8e522a036e38bcf1318cc0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa8ea925033da81a7e7007a7094adcf2c25d3c8749402565b0d1bb7bc9268298 0.600000000000 1513238 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": 1044051, "vin": [ { "gen": { "height": 1044041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa8ea925033da81a7e7007a7094adcf2c25d3c8749402565b0d1bb7bc9268298" } } ], "extra": [ 1, 34, 254, 73, 147, 2, 91, 109, 102, 214, 16, 113, 0, 52, 114, 166, 245, 93, 32, 198, 231, 161, 184, 229, 34, 160, 54, 227, 139, 207, 19, 24, 204, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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