Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad566b3e906c59b93e15a6f09d6d5dcc5d395c437a94bca64d54cd731abf7a4d

Tx prefix hash: 542474629ea34517551e7ecdd56f803c68229488864a3d443e527cb0a49df17d
Tx public key: 0bb3af56f0c53a756d256aaf49c0957a5a23f8f3c15d2d804effe945cd11118a
Timestamp: 1730541198 Timestamp [UCT]: 2024-11-02 09:53:18 Age [y:d:h:m:s]: 00:004:22:48:36
Block: 1144858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3555 RingCT/type: yes/0
Extra: 010bb3af56f0c53a756d256aaf49c0957a5a23f8f3c15d2d804effe945cd11118a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44c7b92d674c4340dd07a5d6099cf0441846ef113e12b900c4cf489059aa4be3 0.600000000000 1629189 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": 1144868, "vin": [ { "gen": { "height": 1144858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44c7b92d674c4340dd07a5d6099cf0441846ef113e12b900c4cf489059aa4be3" } } ], "extra": [ 1, 11, 179, 175, 86, 240, 197, 58, 117, 109, 37, 106, 175, 73, 192, 149, 122, 90, 35, 248, 243, 193, 93, 45, 128, 78, 255, 233, 69, 205, 17, 17, 138, 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