Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b69e1c0535a842099db66a85c2df7b2290e9df75328836bbd6a1ca0a17d14d3

Tx prefix hash: ba2e316d86193fdcfecace857f73310df71aefca0ab8d7034dc5f74dc83efe95
Tx public key: 538cd917402c46619a63acb82dd92b450bbb4ba3112ed2ee33edb5fab5d5d55b
Timestamp: 1712147634 Timestamp [UCT]: 2024-04-03 12:33:54 Age [y:d:h:m:s]: 01:219:15:50:40
Block: 992424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415694 RingCT/type: yes/0
Extra: 01538cd917402c46619a63acb82dd92b450bbb4ba3112ed2ee33edb5fab5d5d55b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2adb83ba182312f070c319cb7824d844aa49261173d8ab1a417c6d1b0761d81 0.600000000000 1452766 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": 992434, "vin": [ { "gen": { "height": 992424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2adb83ba182312f070c319cb7824d844aa49261173d8ab1a417c6d1b0761d81" } } ], "extra": [ 1, 83, 140, 217, 23, 64, 44, 70, 97, 154, 99, 172, 184, 45, 217, 43, 69, 11, 187, 75, 163, 17, 46, 210, 238, 51, 237, 181, 250, 181, 213, 213, 91, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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