Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b3c8afc28c9a87d39e68408c56e4bc4ac43d6698e5718f6f9c5174c785d401

Tx prefix hash: 50673b5423d1f1597979cc047bd025c6d58d44d7da59eb61482409a34d130b7d
Tx public key: a58389224880a39b667447184f4f7e0c2e6d65523b27c7c636f73f724430708f
Timestamp: 1701227264 Timestamp [UCT]: 2023-11-29 03:07:44 Age [y:d:h:m:s]: 01:140:02:02:26
Block: 901914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361285 RingCT/type: yes/0
Extra: 01a58389224880a39b667447184f4f7e0c2e6d65523b27c7c636f73f724430708f0211000000024b8f5122000000000000000000

1 output(s) for total of 0.630353976000 dcy

stealth address amount amount idx
00: b2205deb9581f889e51c95ea4016221e87c2f0b92786f32ea973bd74824eeb4a 0.630353976000 1358511 of 0

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": 901924, "vin": [ { "gen": { "height": 901914 } } ], "vout": [ { "amount": 630353976, "target": { "key": "b2205deb9581f889e51c95ea4016221e87c2f0b92786f32ea973bd74824eeb4a" } } ], "extra": [ 1, 165, 131, 137, 34, 72, 128, 163, 155, 102, 116, 71, 24, 79, 79, 126, 12, 46, 109, 101, 82, 59, 39, 199, 198, 54, 247, 63, 114, 68, 48, 112, 143, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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