Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc64eef81e8c3e8e651d0ae3d887801bbf083cb315d05a49a402de29cef3c35

Tx prefix hash: ad6590b697c94d094467b58655687b70bc0f07756ce4f45b6809451d1f51af19
Tx public key: 5654d1a7adb75967c62b49c1278045e87211e53549418370c179d662f9d3e956
Timestamp: 1732615714 Timestamp [UCT]: 2024-11-26 10:08:34 Age [y:d:h:m:s]: 00:118:13:08:16
Block: 1162041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84530 RingCT/type: yes/0
Extra: 015654d1a7adb75967c62b49c1278045e87211e53549418370c179d662f9d3e956021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5354f63e76dd38ffe2e549136b0bef6509f2b1f2e0b2ec7d2b3fac2ce02b5c40 0.600000000000 1647696 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": 1162051, "vin": [ { "gen": { "height": 1162041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5354f63e76dd38ffe2e549136b0bef6509f2b1f2e0b2ec7d2b3fac2ce02b5c40" } } ], "extra": [ 1, 86, 84, 209, 167, 173, 183, 89, 103, 198, 43, 73, 193, 39, 128, 69, 232, 114, 17, 229, 53, 73, 65, 131, 112, 193, 121, 214, 98, 249, 211, 233, 86, 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