Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 527f71a95754e42ab22381b6367412bb16d04a4a55c169178c4b40c2b72b2ee5

Tx prefix hash: 52a3639013df503505ebe63c3b276f64e988d18d99bae7b95927fd39002630aa
Tx public key: 8d5690212f8c3280ed3434f5fd8f22ea3d7c54cecf13a534956a637c5a4bf810
Timestamp: 1716741279 Timestamp [UCT]: 2024-05-26 16:34:39 Age [y:d:h:m:s]: 00:242:12:40:06
Block: 1030543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173516 RingCT/type: yes/0
Extra: 018d5690212f8c3280ed3434f5fd8f22ea3d7c54cecf13a534956a637c5a4bf8100211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e9d851eb6800525b8ab534fbcd17866937a966634e8305e5d0a1b3e60bb64bb 0.600000000000 1498798 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": 1030553, "vin": [ { "gen": { "height": 1030543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e9d851eb6800525b8ab534fbcd17866937a966634e8305e5d0a1b3e60bb64bb" } } ], "extra": [ 1, 141, 86, 144, 33, 47, 140, 50, 128, 237, 52, 52, 245, 253, 143, 34, 234, 61, 124, 84, 206, 207, 19, 165, 52, 149, 106, 99, 124, 90, 75, 248, 16, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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