Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb93a2b162034dd8f7f786e4b70fe2b78395e717403a4a6edfa9c1da55af2653

Tx prefix hash: a6c8f4ba1b655202f7100eb2dddb2c2f41ba82d57d7142a417f71ed9bfc57150
Tx public key: 85238d9e15a2206000b12089ae0d6a44b76af9ebbffeec7589f2642351b2aea8
Timestamp: 1695934383 Timestamp [UCT]: 2023-09-28 20:53:03 Age [y:d:h:m:s]: 01:216:12:17:55
Block: 858240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415818 RingCT/type: yes/0
Extra: 0185238d9e15a2206000b12089ae0d6a44b76af9ebbffeec7589f2642351b2aea8021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.879619102000 dcy

stealth address amount amount idx
00: ae8ec0fdf9d509a05b7338eb48c9efd8c113bdd26f83c5d37b8d3c9b000fd1f0 0.879619102000 1312408 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": 858250, "vin": [ { "gen": { "height": 858240 } } ], "vout": [ { "amount": 879619102, "target": { "key": "ae8ec0fdf9d509a05b7338eb48c9efd8c113bdd26f83c5d37b8d3c9b000fd1f0" } } ], "extra": [ 1, 133, 35, 141, 158, 21, 162, 32, 96, 0, 177, 32, 137, 174, 13, 106, 68, 183, 106, 249, 235, 191, 254, 236, 117, 137, 242, 100, 35, 81, 178, 174, 168, 2, 17, 0, 0, 0, 7, 230, 210, 127, 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