Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8db4fd49868bc9f52d67d13f38080153ef6ca9c3b453f3ecfe7af3c47a12b687

Tx prefix hash: 6cc473b83631631a1cdaf4612019768a44ae1f7a2decc801db7e44a897424fbe
Tx public key: 4cd1861e4eb62e06cf951e1eaa66254f1cfe970742d5d8cbae667313d34bdd01
Timestamp: 1732661466 Timestamp [UCT]: 2024-11-26 22:51:06 Age [y:d:h:m:s]: 00:115:22:59:02
Block: 1162426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82684 RingCT/type: yes/0
Extra: 014cd1861e4eb62e06cf951e1eaa66254f1cfe970742d5d8cbae667313d34bdd010211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc445915e964d76de9fa0493c5b0b2ee094282f641fce09dfa0d14a4d0e748b7 0.600000000000 1648081 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": 1162436, "vin": [ { "gen": { "height": 1162426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc445915e964d76de9fa0493c5b0b2ee094282f641fce09dfa0d14a4d0e748b7" } } ], "extra": [ 1, 76, 209, 134, 30, 78, 182, 46, 6, 207, 149, 30, 30, 170, 102, 37, 79, 28, 254, 151, 7, 66, 213, 216, 203, 174, 102, 115, 19, 211, 75, 221, 1, 2, 17, 0, 0, 0, 2, 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