Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351ba199dd0861ea738b0ce6ef6208f3230d47c71cbdd03c456b1d4e784f33f9

Tx prefix hash: 22b42cac14b7cca1829c59bb5d6413895c49888d59c5dd45aae89c1da31c66c2
Tx public key: f550104bb4a7b504627d3fb6cb70485926bfc6aac14e17ad8c465f4ce0bb67db
Timestamp: 1730675713 Timestamp [UCT]: 2024-11-03 23:15:13 Age [y:d:h:m:s]: 00:003:09:17:27
Block: 1145975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2433 RingCT/type: yes/0
Extra: 01f550104bb4a7b504627d3fb6cb70485926bfc6aac14e17ad8c465f4ce0bb67db0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 774eaa2d5e8d71a47c6bb018e43b1c550868d253bc527fbf5674280a62dc989c 0.600000000000 1630516 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": 1145985, "vin": [ { "gen": { "height": 1145975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "774eaa2d5e8d71a47c6bb018e43b1c550868d253bc527fbf5674280a62dc989c" } } ], "extra": [ 1, 245, 80, 16, 75, 180, 167, 181, 4, 98, 125, 63, 182, 203, 112, 72, 89, 38, 191, 198, 170, 193, 78, 23, 173, 140, 70, 95, 76, 224, 187, 103, 219, 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