Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f566a3a5d8703d2c5532f1c27ac7585a716cb42cb10635f8b89f9e083add057

Tx prefix hash: e5ac39d582b5e14874eb3ea91e63764663d41d6f83ffc66aacd1c44c61b59dc1
Tx public key: bb41aab5ebdc40f3ab837ac1a671e064dcc7686ea77b9ecb3a0d9634f8f7e41f
Timestamp: 1721712170 Timestamp [UCT]: 2024-07-23 05:22:50 Age [y:d:h:m:s]: 00:256:01:55:47
Block: 1071741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182948 RingCT/type: yes/0
Extra: 01bb41aab5ebdc40f3ab837ac1a671e064dcc7686ea77b9ecb3a0d9634f8f7e41f021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1a43220ce6290f90ff3bdf17f90ccc228c37986eb4760d116282b05c973d3cf 0.600000000000 1544080 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": 1071751, "vin": [ { "gen": { "height": 1071741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1a43220ce6290f90ff3bdf17f90ccc228c37986eb4760d116282b05c973d3cf" } } ], "extra": [ 1, 187, 65, 170, 181, 235, 220, 64, 243, 171, 131, 122, 193, 166, 113, 224, 100, 220, 199, 104, 110, 167, 123, 158, 203, 58, 13, 150, 52, 248, 247, 228, 31, 2, 17, 0, 0, 0, 7, 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