Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b62b8f7f9ddfe4a1ae699447e89ea16a1bb9571a2d8d9cae2cf979f89c0db41

Tx prefix hash: 42093534d8efc073b6c47bcd04d6aeb6fda53857e3b16193327222d1d35a8466
Tx public key: 74dd73af2cffb211ba85b37cf85a3ee6a759b27328ee800bfcb98a3087bfa92f
Timestamp: 1732487851 Timestamp [UCT]: 2024-11-24 22:37:31 Age [y:d:h:m:s]: 00:206:17:27:57
Block: 1160989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147481 RingCT/type: yes/0
Extra: 0174dd73af2cffb211ba85b37cf85a3ee6a759b27328ee800bfcb98a3087bfa92f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96cefd9887ab16be099046513d45ea9bf1b6a7403c6b0190cdf08e28837a7484 0.600000000000 1646640 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": 1160999, "vin": [ { "gen": { "height": 1160989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96cefd9887ab16be099046513d45ea9bf1b6a7403c6b0190cdf08e28837a7484" } } ], "extra": [ 1, 116, 221, 115, 175, 44, 255, 178, 17, 186, 133, 179, 124, 248, 90, 62, 230, 167, 89, 178, 115, 40, 238, 128, 11, 252, 185, 138, 48, 135, 191, 169, 47, 2, 17, 0, 0, 0, 3, 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