Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8bd8446f293cad31164e7a275023479d484c4b613bdd8f1d4adcbb7b2bc0392

Tx prefix hash: 71cef1fe25b74531b62afa4cc78c5fbca2517a05598eb5ee2eb231b264531241
Tx public key: c8fb193e0047a03c316b2e7c40dadb731646d746f874bef6a6a27804b3df1070
Timestamp: 1726493871 Timestamp [UCT]: 2024-09-16 13:37:51 Age [y:d:h:m:s]: 00:202:16:30:07
Block: 1111393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144677 RingCT/type: yes/0
Extra: 01c8fb193e0047a03c316b2e7c40dadb731646d746f874bef6a6a27804b3df1070021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a11ba7eca3dc9255d40a098c1e178658b434ddf68a7a4e4b2306727486301fd2 0.600000000000 1590336 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": 1111403, "vin": [ { "gen": { "height": 1111393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a11ba7eca3dc9255d40a098c1e178658b434ddf68a7a4e4b2306727486301fd2" } } ], "extra": [ 1, 200, 251, 25, 62, 0, 71, 160, 60, 49, 107, 46, 124, 64, 218, 219, 115, 22, 70, 215, 70, 248, 116, 190, 246, 166, 162, 120, 4, 179, 223, 16, 112, 2, 17, 0, 0, 0, 2, 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