Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9cf4cd72a8be4fb534dffd82fff67919d7d3191009fc4a5a22cd69a0f503661

Tx prefix hash: c10a9726276162d83ebb102e47c97d5a1962e131be0a5df96a3371463cea8bfb
Tx public key: 6e4b41ba6b1c370094843b74d6e0005b5005c3029b0d6520dbcad9e08efa6178
Timestamp: 1728814559 Timestamp [UCT]: 2024-10-13 10:15:59 Age [y:d:h:m:s]: 00:164:02:54:21
Block: 1130637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117062 RingCT/type: yes/0
Extra: 016e4b41ba6b1c370094843b74d6e0005b5005c3029b0d6520dbcad9e08efa6178021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb81a8e904becca558fcbe5b79dc6eb2312f1c84abc1e0755d8d4f442f66c69c 0.600000000000 1613514 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": 1130647, "vin": [ { "gen": { "height": 1130637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb81a8e904becca558fcbe5b79dc6eb2312f1c84abc1e0755d8d4f442f66c69c" } } ], "extra": [ 1, 110, 75, 65, 186, 107, 28, 55, 0, 148, 132, 59, 116, 214, 224, 0, 91, 80, 5, 195, 2, 155, 13, 101, 32, 219, 202, 217, 224, 142, 250, 97, 120, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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