Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86e5e6a9acf080c9f60017fb1e19a81edb0baf495e697527bdbd0d7104947962

Tx prefix hash: 5b2a69d2eac0b15f118f66bca9bd795393600f76f54195cb415c82402fcd50a8
Tx public key: 7997c4c8d3f10fe60e5d7b6224c8d21172bba4899dce0f367cc2607e42d45299
Timestamp: 1733507058 Timestamp [UCT]: 2024-12-06 17:44:18 Age [y:d:h:m:s]: 00:102:20:41:48
Block: 1169436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73324 RingCT/type: yes/0
Extra: 017997c4c8d3f10fe60e5d7b6224c8d21172bba4899dce0f367cc2607e42d452990211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e351ef41cac6e3952ff98f70a21fda359fb54c458b24d29e6b37ba621cca42c1 0.600000000000 1655153 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": 1169446, "vin": [ { "gen": { "height": 1169436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e351ef41cac6e3952ff98f70a21fda359fb54c458b24d29e6b37ba621cca42c1" } } ], "extra": [ 1, 121, 151, 196, 200, 211, 241, 15, 230, 14, 93, 123, 98, 36, 200, 210, 17, 114, 187, 164, 137, 157, 206, 15, 54, 124, 194, 96, 126, 66, 212, 82, 153, 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