Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a5831223c3537eafb1f1afcfaace29fa77dc288a5a4f99c676a8850716f4699

Tx prefix hash: 97af0fdac8e48c77c4d6d680e964a140f4813646392aabe06b8bd5b0da17c8a1
Tx public key: f57c0ae161def352b110e9036ee9f3c7d6bab8d8097d323748ad8a7ed2d43825
Timestamp: 1722181937 Timestamp [UCT]: 2024-07-28 15:52:17 Age [y:d:h:m:s]: 00:306:09:58:40
Block: 1075645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218940 RingCT/type: yes/0
Extra: 01f57c0ae161def352b110e9036ee9f3c7d6bab8d8097d323748ad8a7ed2d4382502110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bc48fc9c7c1e137f82a84848b219544a96762866300b03d000b0bb15503b672 0.600000000000 1548174 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": 1075655, "vin": [ { "gen": { "height": 1075645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bc48fc9c7c1e137f82a84848b219544a96762866300b03d000b0bb15503b672" } } ], "extra": [ 1, 245, 124, 10, 225, 97, 222, 243, 82, 177, 16, 233, 3, 110, 233, 243, 199, 214, 186, 184, 216, 9, 125, 50, 55, 72, 173, 138, 126, 210, 212, 56, 37, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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