Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ad5f56f866fe832ce9078fc7247f1984d29b6afe2623430a187b30d95b2ae52

Tx prefix hash: c37ad5b8e92602bfd7086f4be451175e792f2f55c6ae949c76bf3a37fb7a7bb3
Tx public key: b5e286be387f3227430f574c597f324db78138ad7bb58953d7e9df4bb0a60e4a
Timestamp: 1737139782 Timestamp [UCT]: 2025-01-17 18:49:42 Age [y:d:h:m:s]: 00:058:16:24:54
Block: 1199502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41734 RingCT/type: yes/0
Extra: 01b5e286be387f3227430f574c597f324db78138ad7bb58953d7e9df4bb0a60e4a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b684122431fc3513c0f936d6948f079cdb8c28885b6733863e1d589e50d840 0.600000000000 1686133 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": 1199512, "vin": [ { "gen": { "height": 1199502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b684122431fc3513c0f936d6948f079cdb8c28885b6733863e1d589e50d840" } } ], "extra": [ 1, 181, 226, 134, 190, 56, 127, 50, 39, 67, 15, 87, 76, 89, 127, 50, 77, 183, 129, 56, 173, 123, 181, 137, 83, 215, 233, 223, 75, 176, 166, 14, 74, 2, 17, 0, 0, 0, 7, 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