Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88a9264aa468ca93bc398c0f9c41ef071a8576c65f6f4aff416f3967a78cab68

Tx prefix hash: eff02c2d71f2aac1dd52e2e3b6a0e64ec824083c660b84a7471af39e7e85b456
Tx public key: d553b1c4417f838555ae529b7292ddebdd8249349d230bbc398b540d3f274b14
Timestamp: 1684969625 Timestamp [UCT]: 2023-05-24 23:07:05 Age [y:d:h:m:s]: 01:234:03:41:45
Block: 767394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428769 RingCT/type: yes/0
Extra: 01d553b1c4417f838555ae529b7292ddebdd8249349d230bbc398b540d3f274b14021100000001faf35c9c000000000000000000

1 output(s) for total of 1.759159813000 dcy

stealth address amount amount idx
00: e45b28e13700a0cd243b6431820b9a2e8d583b81ff944c4195f4682ca0d4edc5 1.759159813000 1216515 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": 767404, "vin": [ { "gen": { "height": 767394 } } ], "vout": [ { "amount": 1759159813, "target": { "key": "e45b28e13700a0cd243b6431820b9a2e8d583b81ff944c4195f4682ca0d4edc5" } } ], "extra": [ 1, 213, 83, 177, 196, 65, 127, 131, 133, 85, 174, 82, 155, 114, 146, 221, 235, 221, 130, 73, 52, 157, 35, 11, 188, 57, 139, 84, 13, 63, 39, 75, 20, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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