Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d5a30e4811e3a5a62930792a419b37fd637c00fa7c17c684ca940d68eefb3f8

Tx prefix hash: d0f89d2380ed0405d2d8ef711559713cd34cd0c7dd2b5a399a5b8dff730daa79
Tx public key: 1eb28ffd3bc21103a96a9fd901e03c4653bdb020f9a42f331236024a08a43130
Timestamp: 1726009641 Timestamp [UCT]: 2024-09-10 23:07:21 Age [y:d:h:m:s]: 00:102:20:16:02
Block: 1107380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73577 RingCT/type: yes/0
Extra: 011eb28ffd3bc21103a96a9fd901e03c4653bdb020f9a42f331236024a08a43130021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c1b682bbd376e94cb3961a7c43ee7fe1e3201b0f46a7cedfe95fe7064866ef 0.600000000000 1584991 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": 1107390, "vin": [ { "gen": { "height": 1107380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c1b682bbd376e94cb3961a7c43ee7fe1e3201b0f46a7cedfe95fe7064866ef" } } ], "extra": [ 1, 30, 178, 143, 253, 59, 194, 17, 3, 169, 106, 159, 217, 1, 224, 60, 70, 83, 189, 176, 32, 249, 164, 47, 51, 18, 54, 2, 74, 8, 164, 49, 48, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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