Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2568af39ac78fb40c58f7e156f4f5f9251f9bf7f1f5e7dff28f24579969eb7c7

Tx prefix hash: 28bbb645faac8caa0d384c38444c34e5c38286ae104c844ec569faadc65c1df6
Tx public key: 731aaa4352cf54343cae0fb44115019c43648eabee2bfb04d8fba4e1cb3e7aa7
Timestamp: 1715141436 Timestamp [UCT]: 2024-05-08 04:10:36 Age [y:d:h:m:s]: 00:190:04:43:47
Block: 1017279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136137 RingCT/type: yes/0
Extra: 01731aaa4352cf54343cae0fb44115019c43648eabee2bfb04d8fba4e1cb3e7aa70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f22d2892ab65510a14d9125267ccf623a9450c6a8aec66e656ac1e2418263d6 0.600000000000 1481050 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": 1017289, "vin": [ { "gen": { "height": 1017279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f22d2892ab65510a14d9125267ccf623a9450c6a8aec66e656ac1e2418263d6" } } ], "extra": [ 1, 115, 26, 170, 67, 82, 207, 84, 52, 60, 174, 15, 180, 65, 21, 1, 156, 67, 100, 142, 171, 238, 43, 251, 4, 216, 251, 164, 225, 203, 62, 122, 167, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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