Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283ace19503c634702384e552d63ba2fa46a8c1e71949ff31a7d7b8b9a26b7b2

Tx prefix hash: d81fc579b95b30400e3263fe9e505b4e19bc2f31cf6958a8cd866ec6c258fa1a
Tx public key: f8cf1414c2b296dc1580d8b1099a46365aacdf031f6ec14ddad93bd0e11fcc93
Timestamp: 1733480671 Timestamp [UCT]: 2024-12-06 10:24:31 Age [y:d:h:m:s]: 00:335:03:33:41
Block: 1169214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237024 RingCT/type: yes/0
Extra: 01f8cf1414c2b296dc1580d8b1099a46365aacdf031f6ec14ddad93bd0e11fcc93021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c68c90d89112f9c0cc8ce57453e537c7b2a0e01bdf57950b96af01ec8c5ea7 0.600000000000 1654929 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": 1169224, "vin": [ { "gen": { "height": 1169214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c68c90d89112f9c0cc8ce57453e537c7b2a0e01bdf57950b96af01ec8c5ea7" } } ], "extra": [ 1, 248, 207, 20, 20, 194, 178, 150, 220, 21, 128, 216, 177, 9, 154, 70, 54, 90, 172, 223, 3, 31, 110, 193, 77, 218, 217, 59, 208, 225, 31, 204, 147, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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