Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac1cf75dad5a4dbea7cb73c2cf6bbb5b1c4ec02eccad881325283fa310633d9a

Tx prefix hash: 5dfac991fd93e9b9dfd479144e3baf4bcc37dc9ca56ff9e50b77f0df46933677
Tx public key: bd020305d925c8f0ab9c0fe9b702c4f779b31332ce3f7b779375c27b5911c415
Timestamp: 1730845703 Timestamp [UCT]: 2024-11-05 22:28:23 Age [y:d:h:m:s]: 01:004:22:16:37
Block: 1147375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261949 RingCT/type: yes/0
Extra: 01bd020305d925c8f0ab9c0fe9b702c4f779b31332ce3f7b779375c27b5911c415021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb43b4ec23b8f5ffed758abd72826690e6ca660511f2fe45ceed592b1f6a45f 0.600000000000 1632070 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": 1147385, "vin": [ { "gen": { "height": 1147375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb43b4ec23b8f5ffed758abd72826690e6ca660511f2fe45ceed592b1f6a45f" } } ], "extra": [ 1, 189, 2, 3, 5, 217, 37, 200, 240, 171, 156, 15, 233, 183, 2, 196, 247, 121, 179, 19, 50, 206, 63, 123, 119, 147, 117, 194, 123, 89, 17, 196, 21, 2, 17, 0, 0, 0, 8, 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