Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6cc651238ad68f76ecf57c4b2891be19ab087b71a7a5da7ca1c01f083d1ad15

Tx prefix hash: 6dd2a5ee6146abb941ddaf26762df9d9f11a5d2b2cfef2f4434d86459f39fc3d
Tx public key: 9b0f74b6303683a2f67eeee007764af57f4379d650f4e5a9c90d1ba8d55a657b
Timestamp: 1726292811 Timestamp [UCT]: 2024-09-14 05:46:51 Age [y:d:h:m:s]: 00:118:06:56:44
Block: 1109724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84589 RingCT/type: yes/0
Extra: 019b0f74b6303683a2f67eeee007764af57f4379d650f4e5a9c90d1ba8d55a657b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7462c102f2c123a410a2bd0836bac89f0f7272bdd30871d71ed6a9086ef1e06a 0.600000000000 1588079 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": 1109734, "vin": [ { "gen": { "height": 1109724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7462c102f2c123a410a2bd0836bac89f0f7272bdd30871d71ed6a9086ef1e06a" } } ], "extra": [ 1, 155, 15, 116, 182, 48, 54, 131, 162, 246, 126, 238, 224, 7, 118, 74, 245, 127, 67, 121, 214, 80, 244, 229, 169, 201, 13, 27, 168, 213, 90, 101, 123, 2, 17, 0, 0, 0, 3, 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