Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e075e83d7a1be2d08dc8fd8a3ef09aae634729e7c920fb034667d807564fac11

Tx prefix hash: ee733a6ecd7204607424154bb0afbe33feb07131050ce50217f7396015333232
Tx public key: 5d10cd37b54e5ba8ea2f990139b5b727d9de323cc3275b46acabf75346b280d8
Timestamp: 1694600387 Timestamp [UCT]: 2023-09-13 10:19:47 Age [y:d:h:m:s]: 01:206:04:39:00
Block: 847165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408449 RingCT/type: yes/0
Extra: 015d10cd37b54e5ba8ea2f990139b5b727d9de323cc3275b46acabf75346b280d802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.957173664000 dcy

stealth address amount amount idx
00: b88ce8354de5d904f7ffd6e10dc883fcc1a3b4412c673469ca080f60512ed257 0.957173664000 1300667 of 0

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": 847175, "vin": [ { "gen": { "height": 847165 } } ], "vout": [ { "amount": 957173664, "target": { "key": "b88ce8354de5d904f7ffd6e10dc883fcc1a3b4412c673469ca080f60512ed257" } } ], "extra": [ 1, 93, 16, 205, 55, 181, 78, 91, 168, 234, 47, 153, 1, 57, 181, 183, 39, 217, 222, 50, 60, 195, 39, 91, 70, 172, 171, 247, 83, 70, 178, 128, 216, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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