Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78036a4923ea388a6f6b5a071d9d40e5643e2f520ef433f4aed2942c76d68640

Tx prefix hash: cd535a2f7b1e35234449f2fce6f6528c6533f99a24d7320b1f3924bc01d41c79
Tx public key: 630454ba0b0e4787cc048dbc9f990a603929ceb9efa14efb9ba2188e07d0fa77
Timestamp: 1707331188 Timestamp [UCT]: 2024-02-07 18:39:48 Age [y:d:h:m:s]: 01:018:15:26:25
Block: 952518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274346 RingCT/type: yes/0
Extra: 01630454ba0b0e4787cc048dbc9f990a603929ceb9efa14efb9ba2188e07d0fa7702110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b01e6c7366d5f59437e7bb390c9bf87955be00c68c2d6e74bd3dbd9f6b85103 0.600000000000 1411544 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": 952528, "vin": [ { "gen": { "height": 952518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b01e6c7366d5f59437e7bb390c9bf87955be00c68c2d6e74bd3dbd9f6b85103" } } ], "extra": [ 1, 99, 4, 84, 186, 11, 14, 71, 135, 204, 4, 141, 188, 159, 153, 10, 96, 57, 41, 206, 185, 239, 161, 78, 251, 155, 162, 24, 142, 7, 208, 250, 119, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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