Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c7c642ce33578d75fd5fe2f986a73f38f99c45775d2f44c8a603469f1997639

Tx prefix hash: 798fd6917edfec23d42c4a4f267f9d5d458850ef1b23185b7f69259b966b535c
Tx public key: 3908009c17671fabb1cd9a1d910a745f73c21519912db4abe7396cb674404d75
Timestamp: 1704157476 Timestamp [UCT]: 2024-01-02 01:04:36 Age [y:d:h:m:s]: 01:096:00:16:54
Block: 926207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329717 RingCT/type: yes/0
Extra: 013908009c17671fabb1cd9a1d910a745f73c21519912db4abe7396cb674404d750211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 468bae80ae10fdb1f7b2bab6d452e2d56c7f4552a22cc6ec685f0b4b1d85129a 0.600000000000 1383981 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": 926217, "vin": [ { "gen": { "height": 926207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "468bae80ae10fdb1f7b2bab6d452e2d56c7f4552a22cc6ec685f0b4b1d85129a" } } ], "extra": [ 1, 57, 8, 0, 156, 23, 103, 31, 171, 177, 205, 154, 29, 145, 10, 116, 95, 115, 194, 21, 25, 145, 45, 180, 171, 231, 57, 108, 182, 116, 64, 77, 117, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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