Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad7c425042c552cae193c89eb48f2ff776084ae9833d318d10a09777fa2eaa30

Tx prefix hash: 007237d48436bb2c1a25b42b5090fb4283f57d731e2d728402b58e42b43d094b
Tx public key: f8b3e8243e9cde889586f012d7cf7cf77b94ce7e71b32b0023f08bea002cde2b
Timestamp: 1728162973 Timestamp [UCT]: 2024-10-05 21:16:13 Age [y:d:h:m:s]: 00:257:17:31:31
Block: 1125233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183879 RingCT/type: yes/0
Extra: 01f8b3e8243e9cde889586f012d7cf7cf77b94ce7e71b32b0023f08bea002cde2b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65fba5d831c654f03881fc68beaba850ae5918d8a7572ae77cd7fa80c164be37 0.600000000000 1607910 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": 1125243, "vin": [ { "gen": { "height": 1125233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65fba5d831c654f03881fc68beaba850ae5918d8a7572ae77cd7fa80c164be37" } } ], "extra": [ 1, 248, 179, 232, 36, 62, 156, 222, 136, 149, 134, 240, 18, 215, 207, 124, 247, 123, 148, 206, 126, 113, 179, 43, 0, 35, 240, 139, 234, 0, 44, 222, 43, 2, 17, 0, 0, 0, 2, 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