Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e09cbc49753a9a5da14f47c2332034f5f4a441933683a403d14dc095bf7d7b0

Tx prefix hash: 928d5f1065005d3e7e48ec2c6ef3156e32ab74bda5e19f5b06358354146d249f
Tx public key: 731f0fc9a3770bf5996078153dddc70ea0a56e94b4aece14c3c2e0a173223918
Timestamp: 1706757461 Timestamp [UCT]: 2024-02-01 03:17:41 Age [y:d:h:m:s]: 00:349:20:54:36
Block: 947751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250480 RingCT/type: yes/0
Extra: 01731f0fc9a3770bf5996078153dddc70ea0a56e94b4aece14c3c2e0a17322391802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 364cc646df5ae41027d5856a53b785fd896429c0e33c574f42169fbdb816943c 0.600000000000 1406109 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": 947761, "vin": [ { "gen": { "height": 947751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "364cc646df5ae41027d5856a53b785fd896429c0e33c574f42169fbdb816943c" } } ], "extra": [ 1, 115, 31, 15, 201, 163, 119, 11, 245, 153, 96, 120, 21, 61, 221, 199, 14, 160, 165, 110, 148, 180, 174, 206, 20, 195, 194, 224, 161, 115, 34, 57, 24, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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