Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 052078c947ed8d6be4fcbbd8bb66cf9ec408b3b88a4ae4b0742cd0ea0dce48e0

Tx prefix hash: 2b6efee21d4253f190d4de36329b9e319247d8d04b8602c2bfff01d42bae600b
Tx public key: 08a9f63265c02826ab52f57c9e61e8a82d79bbf5f69bab0709ee0415f36d0122
Timestamp: 1736322372 Timestamp [UCT]: 2025-01-08 07:46:12 Age [y:d:h:m:s]: 00:161:03:40:27
Block: 1192737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114881 RingCT/type: yes/0
Extra: 0108a9f63265c02826ab52f57c9e61e8a82d79bbf5f69bab0709ee0415f36d0122021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eedb4077fa13f321351addb5fc61e2cf18df39746c7a57fdf60d34e5b78e0ec 0.600000000000 1679292 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": 1192747, "vin": [ { "gen": { "height": 1192737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eedb4077fa13f321351addb5fc61e2cf18df39746c7a57fdf60d34e5b78e0ec" } } ], "extra": [ 1, 8, 169, 246, 50, 101, 192, 40, 38, 171, 82, 245, 124, 158, 97, 232, 168, 45, 121, 187, 245, 246, 155, 171, 7, 9, 238, 4, 21, 243, 109, 1, 34, 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