Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6027ddcfdcb9b099bdea87648c70e64b5d1859cb74dceac50f3935cb717f0707

Tx prefix hash: f6041f1ecb6e285b283b78811d88b760d6dbc2263720d4ca9c12ad5674f4a5a2
Tx public key: 171577e59ba249b7467af131516e2c8b4f88cc7ee4f4366b055320dcc32cf2d0
Timestamp: 1738205129 Timestamp [UCT]: 2025-01-30 02:45:29 Age [y:d:h:m:s]: 00:321:02:43:15
Block: 1208065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227291 RingCT/type: yes/0
Extra: 01171577e59ba249b7467af131516e2c8b4f88cc7ee4f4366b055320dcc32cf2d0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95ff76d9853d509e7d7ea7cf6bfc541afecf81d3ec6abfee21417193e929f213 0.600000000000 1694792 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": 1208075, "vin": [ { "gen": { "height": 1208065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95ff76d9853d509e7d7ea7cf6bfc541afecf81d3ec6abfee21417193e929f213" } } ], "extra": [ 1, 23, 21, 119, 229, 155, 162, 73, 183, 70, 122, 241, 49, 81, 110, 44, 139, 79, 136, 204, 126, 228, 244, 54, 107, 5, 83, 32, 220, 195, 44, 242, 208, 2, 17, 0, 0, 0, 2, 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