Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdb0e00982ae4f6c427de9f257238d763c8ae905f0a9f94c2fe0ff14221bbd53

Tx prefix hash: 82c40707379024d3370f9fd1e6e0aa1486aeb0404e9fb57b66b27332973ef615
Tx public key: 4a4613137c748d2b9e105644228e20e779e5cc26359694b456ea485e609bc805
Timestamp: 1697588937 Timestamp [UCT]: 2023-10-18 00:28:57 Age [y:d:h:m:s]: 01:162:13:34:24
Block: 871956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377206 RingCT/type: yes/0
Extra: 014a4613137c748d2b9e105644228e20e779e5cc26359694b456ea485e609bc80502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.792223700000 dcy

stealth address amount amount idx
00: 0a56f90b3ffcca40c9d8f10a11c3a3c5e2587832dc23844bfbcb61ccba903a92 0.792223700000 1326991 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": 871966, "vin": [ { "gen": { "height": 871956 } } ], "vout": [ { "amount": 792223700, "target": { "key": "0a56f90b3ffcca40c9d8f10a11c3a3c5e2587832dc23844bfbcb61ccba903a92" } } ], "extra": [ 1, 74, 70, 19, 19, 124, 116, 141, 43, 158, 16, 86, 68, 34, 142, 32, 231, 121, 229, 204, 38, 53, 150, 148, 180, 86, 234, 72, 94, 96, 155, 200, 5, 2, 17, 0, 0, 0, 1, 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