Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ceae4beab85d9b76c58996481bc2eb3e7a9083c5d3ae6531d5442ed5e759d4

Tx prefix hash: 9e76afc700d9321374751344cb07c5979983b29cf7a15d7ce4519da0d7b90631
Tx public key: 9feee23c1979839c7ae30882fda488bcf03ae18d9c0cc3831f72fa58a51405a2
Timestamp: 1737323199 Timestamp [UCT]: 2025-01-19 21:46:39 Age [y:d:h:m:s]: 00:151:00:19:30
Block: 1200982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107648 RingCT/type: yes/0
Extra: 019feee23c1979839c7ae30882fda488bcf03ae18d9c0cc3831f72fa58a51405a20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59f91edd5d80a2d939c1218f22fabfb6900249e8a2fb23f58532cbf077da3490 0.600000000000 1687629 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": 1200992, "vin": [ { "gen": { "height": 1200982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59f91edd5d80a2d939c1218f22fabfb6900249e8a2fb23f58532cbf077da3490" } } ], "extra": [ 1, 159, 238, 226, 60, 25, 121, 131, 156, 122, 227, 8, 130, 253, 164, 136, 188, 240, 58, 225, 141, 156, 12, 195, 131, 31, 114, 250, 88, 165, 20, 5, 162, 2, 17, 0, 0, 0, 1, 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