Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8f78feb1a23d5200bb5976d514429711e56eceee2134721e561f4b600b8afb

Tx prefix hash: 2f686876481600337e2c8848ac12add7b3dcc1b4bad13c727a03549b23f99396
Tx public key: c4cd989f8750b193299a58cc28bdc7036c526c3d5c6e4be8bb9c6d655bbb509b
Timestamp: 1715865856 Timestamp [UCT]: 2024-05-16 13:24:16 Age [y:d:h:m:s]: 01:009:02:36:57
Block: 1023283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267437 RingCT/type: yes/0
Extra: 01c4cd989f8750b193299a58cc28bdc7036c526c3d5c6e4be8bb9c6d655bbb509b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24b4f178af5052bff75f7d676402a75128be6e52bbd960b0cd2be1c8b4ea78e1 0.600000000000 1488150 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": 1023293, "vin": [ { "gen": { "height": 1023283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24b4f178af5052bff75f7d676402a75128be6e52bbd960b0cd2be1c8b4ea78e1" } } ], "extra": [ 1, 196, 205, 152, 159, 135, 80, 177, 147, 41, 154, 88, 204, 40, 189, 199, 3, 108, 82, 108, 61, 92, 110, 75, 232, 187, 156, 109, 101, 91, 187, 80, 155, 2, 17, 0, 0, 0, 5, 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