Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cd13fbee1d32b3f26ec5e26f1e91c25d48af88130d11e07c22edce161d88aeb

Tx prefix hash: ba8d2114486d02b84ecab9a10e4be9e969f1a1412337e8beb420d66a30e5c07e
Tx public key: 3902c5b04535e9a8886c1e8abd67d084c0017282eea65f094afcbc63c1634668
Timestamp: 1731663971 Timestamp [UCT]: 2024-11-15 09:46:11 Age [y:d:h:m:s]: 00:161:01:02:49
Block: 1154165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114938 RingCT/type: yes/0
Extra: 013902c5b04535e9a8886c1e8abd67d084c0017282eea65f094afcbc63c1634668021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cccad3cbc5f75241ab26bc55ad92e8d8f2542bd78afa779e7504634d9b92d4a 0.600000000000 1639776 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": 1154175, "vin": [ { "gen": { "height": 1154165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cccad3cbc5f75241ab26bc55ad92e8d8f2542bd78afa779e7504634d9b92d4a" } } ], "extra": [ 1, 57, 2, 197, 176, 69, 53, 233, 168, 136, 108, 30, 138, 189, 103, 208, 132, 192, 1, 114, 130, 238, 166, 95, 9, 74, 252, 188, 99, 193, 99, 70, 104, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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