Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c56c371e06521ef9e209787f0b044834a1b291c3e169e4b5e51f17b4d2a1481

Tx prefix hash: 9898e36c02e561049c9e9cb055229c5b295e6d2f9f35fe24001b168ddff8efa5
Tx public key: 7482a1f544943689748683e469dc4b9ad874fcf0b2b89a9da7a76f0408e84422
Timestamp: 1736580891 Timestamp [UCT]: 2025-01-11 07:34:51 Age [y:d:h:m:s]: 00:095:00:49:29
Block: 1194877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67709 RingCT/type: yes/0
Extra: 017482a1f544943689748683e469dc4b9ad874fcf0b2b89a9da7a76f0408e84422021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b61963516d8dde789c3b823c790be40da7cd2d3263aa0fac98ed249f8b9c49ec 0.600000000000 1681456 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": 1194887, "vin": [ { "gen": { "height": 1194877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b61963516d8dde789c3b823c790be40da7cd2d3263aa0fac98ed249f8b9c49ec" } } ], "extra": [ 1, 116, 130, 161, 245, 68, 148, 54, 137, 116, 134, 131, 228, 105, 220, 75, 154, 216, 116, 252, 240, 178, 184, 154, 157, 167, 167, 111, 4, 8, 232, 68, 34, 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