Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a14dc8145bced512b30296138391c517e3dd4b7c3ac16cdbd944e18bea26752

Tx prefix hash: 0bad8af64be65f4415ead66b616a6defcef3812f55471886dafa292d49be48b9
Tx public key: 7080630e4dfa01a2e1df32ea794b9999ae18cec317a7637f86fe56a84d84ed67
Timestamp: 1736680349 Timestamp [UCT]: 2025-01-12 11:12:29 Age [y:d:h:m:s]: 00:157:04:49:59
Block: 1195700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112061 RingCT/type: yes/0
Extra: 017080630e4dfa01a2e1df32ea794b9999ae18cec317a7637f86fe56a84d84ed670211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfa1f031d4d31b5521f0c68b14f81ab8ff2c6d57347a837b2b52384932e5279c 0.600000000000 1682291 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": 1195710, "vin": [ { "gen": { "height": 1195700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfa1f031d4d31b5521f0c68b14f81ab8ff2c6d57347a837b2b52384932e5279c" } } ], "extra": [ 1, 112, 128, 99, 14, 77, 250, 1, 162, 225, 223, 50, 234, 121, 75, 153, 153, 174, 24, 206, 195, 23, 167, 99, 127, 134, 254, 86, 168, 77, 132, 237, 103, 2, 17, 0, 0, 0, 6, 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