Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33fffae0953a7f31824258b86008c76fe0d7b03fcc1608ebd4c404ffc492284a

Tx prefix hash: 736d95f958a8cc174799c29200ea6fe454a1c8702e16b36f358cbbee09e9ac9c
Tx public key: c16d95f490c5148a23732a133a0bc478cd7d3222a3c098b79f14f7ebed9b6e67
Timestamp: 1731386167 Timestamp [UCT]: 2024-11-12 04:36:07 Age [y:d:h:m:s]: 00:102:18:38:54
Block: 1151859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73238 RingCT/type: yes/0
Extra: 01c16d95f490c5148a23732a133a0bc478cd7d3222a3c098b79f14f7ebed9b6e67021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8b57154953277c25419d946a25e67ccfa520a814bf9b9d29bde55243bd0c018 0.600000000000 1637442 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": 1151869, "vin": [ { "gen": { "height": 1151859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8b57154953277c25419d946a25e67ccfa520a814bf9b9d29bde55243bd0c018" } } ], "extra": [ 1, 193, 109, 149, 244, 144, 197, 20, 138, 35, 115, 42, 19, 58, 11, 196, 120, 205, 125, 50, 34, 163, 192, 152, 183, 159, 20, 247, 235, 237, 155, 110, 103, 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