Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56f189e1ecb92039da26215fa8b245e6a8e1c79cfb4475eef5cf3f32e2b961e0

Tx prefix hash: 0776bf11b03186167ecb98d8f9ba9402e055db13520d82f3a70b9c6b88e90d4e
Tx public key: 602e84ea0f0870d9164c0e751765e13386f5bd031efbf74d0062c78772625b77
Timestamp: 1737160433 Timestamp [UCT]: 2025-01-18 00:33:53 Age [y:d:h:m:s]: 00:154:09:39:35
Block: 1199671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110013 RingCT/type: yes/0
Extra: 01602e84ea0f0870d9164c0e751765e13386f5bd031efbf74d0062c78772625b770211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ebb91ae2f762c3a325c58ce9868025921ba0ef07e9bdd0800fa1388e2b144f9 0.600000000000 1686304 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": 1199681, "vin": [ { "gen": { "height": 1199671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ebb91ae2f762c3a325c58ce9868025921ba0ef07e9bdd0800fa1388e2b144f9" } } ], "extra": [ 1, 96, 46, 132, 234, 15, 8, 112, 217, 22, 76, 14, 117, 23, 101, 225, 51, 134, 245, 189, 3, 30, 251, 247, 77, 0, 98, 199, 135, 114, 98, 91, 119, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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