Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c219592cb7e9247847af1139bfda0526e3a65f1edc20a6ff8548c5618422e70

Tx prefix hash: ffa0d5b621eece6f91bb401d79559e0eecbc5c9c39fd9675c093c31b5006ab92
Tx public key: ba938966a10651a29ae49e104f76b25140ed44aa9b8c2741ee2d79a329cedd6f
Timestamp: 1730752455 Timestamp [UCT]: 2024-11-04 20:34:15 Age [y:d:h:m:s]: 00:002:16:09:41
Block: 1146602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1929 RingCT/type: yes/0
Extra: 01ba938966a10651a29ae49e104f76b25140ed44aa9b8c2741ee2d79a329cedd6f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a332e038565008a5e0dc416bf58f343d1703f5d24231a30da6292c5b7f2ea9 0.600000000000 1631283 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": 1146612, "vin": [ { "gen": { "height": 1146602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a332e038565008a5e0dc416bf58f343d1703f5d24231a30da6292c5b7f2ea9" } } ], "extra": [ 1, 186, 147, 137, 102, 161, 6, 81, 162, 154, 228, 158, 16, 79, 118, 178, 81, 64, 237, 68, 170, 155, 140, 39, 65, 238, 45, 121, 163, 41, 206, 221, 111, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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