Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a10009e208aa927b84f9fe124ed454c69767c99788bb038c0d221f2577a22dc2

Tx prefix hash: a0c5bf4a14d1b4d76bd4515aab7d033cb0bd9bfc5fd666cb8c63cb7d3d50aaca
Tx public key: b171decc6ba6bbcc281eaff5b6e99f4b90743dd1eadd2457a6a108559f5222fd
Timestamp: 1725149439 Timestamp [UCT]: 2024-09-01 00:10:39 Age [y:d:h:m:s]: 00:214:22:51:50
Block: 1100241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153474 RingCT/type: yes/0
Extra: 01b171decc6ba6bbcc281eaff5b6e99f4b90743dd1eadd2457a6a108559f5222fd02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8a8be26f610b320fc012d0454684aeb8dfb909d73addac24be25603497d1173 0.600000000000 1576216 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": 1100251, "vin": [ { "gen": { "height": 1100241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8a8be26f610b320fc012d0454684aeb8dfb909d73addac24be25603497d1173" } } ], "extra": [ 1, 177, 113, 222, 204, 107, 166, 187, 204, 40, 30, 175, 245, 182, 233, 159, 75, 144, 116, 61, 209, 234, 221, 36, 87, 166, 161, 8, 85, 159, 82, 34, 253, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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