Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 701385737d552910d9ed56df03398fb1f79f38cf32bb7e4a57d2da66a9cc5394

Tx prefix hash: cce6aa0d10fe4ecd397c2b5373c1cd3e6d3045c9d3453fa35fd1897fd0091e83
Tx public key: 99e9b782b1dec29de2fb499cb2fffa15eda18ae037b538031aafb2d034384bb1
Timestamp: 1714175286 Timestamp [UCT]: 2024-04-26 23:48:06 Age [y:d:h:m:s]: 01:035:23:22:33
Block: 1009252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286687 RingCT/type: yes/0
Extra: 0199e9b782b1dec29de2fb499cb2fffa15eda18ae037b538031aafb2d034384bb102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 548937f01818fa2d7d1d1eeadc9d53654b36356b7041bc09472b21069f63af67 0.600000000000 1470872 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": 1009262, "vin": [ { "gen": { "height": 1009252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "548937f01818fa2d7d1d1eeadc9d53654b36356b7041bc09472b21069f63af67" } } ], "extra": [ 1, 153, 233, 183, 130, 177, 222, 194, 157, 226, 251, 73, 156, 178, 255, 250, 21, 237, 161, 138, 224, 55, 181, 56, 3, 26, 175, 178, 208, 52, 56, 75, 177, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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