Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd1a79f6c74298a2d5fef5e058f27cab429662858b685cfdef8234acf0644ecc

Tx prefix hash: 875fd16988a507c0fa4086b0cfc2fe2f4cade3548e443be8fdc2a90b2f27bb21
Tx public key: c94f019afee472470012f2f8eed091cda58a5398447368cb5bfb2c7217b5a3c6
Timestamp: 1682348662 Timestamp [UCT]: 2023-04-24 15:04:22 Age [y:d:h:m:s]: 01:359:18:32:18
Block: 745657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518402 RingCT/type: yes/0
Extra: 01c94f019afee472470012f2f8eed091cda58a5398447368cb5bfb2c7217b5a3c6021100000003b3164c24000000000000000000

1 output(s) for total of 2.076486116000 dcy

stealth address amount amount idx
00: 64982654687e91130fbfe8c4984a2afa2550a0c6d8ffba7daad25aedda62a44d 2.076486116000 1193128 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": 745667, "vin": [ { "gen": { "height": 745657 } } ], "vout": [ { "amount": 2076486116, "target": { "key": "64982654687e91130fbfe8c4984a2afa2550a0c6d8ffba7daad25aedda62a44d" } } ], "extra": [ 1, 201, 79, 1, 154, 254, 228, 114, 71, 0, 18, 242, 248, 238, 208, 145, 205, 165, 138, 83, 152, 68, 115, 104, 203, 91, 251, 44, 114, 23, 181, 163, 198, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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