Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f31b15ead9e48b60c1837a13d18610f8bd52d5156904fdf08b29dda7e508a38a

Tx prefix hash: 64fc96e1b1210cb9c5055e2288b8fe7b0d8ae806b03600cf9502681f1c6c6c3e
Tx public key: 351248cc9c3bd3d19a1c3e17660a1315534346a65178e6629caf9eb2f4b3003d
Timestamp: 1684351077 Timestamp [UCT]: 2023-05-17 19:17:57 Age [y:d:h:m:s]: 01:282:19:36:40
Block: 762260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463303 RingCT/type: yes/0
Extra: 01351248cc9c3bd3d19a1c3e17660a1315534346a65178e6629caf9eb2f4b3003d021100000009e6d27f9c000000000000000000

1 output(s) for total of 1.829432441000 dcy

stealth address amount amount idx
00: 802620e1f61a97e35c4cb0c16132c4d139b4fee9b51b1db738d3fa06b36c7d6f 1.829432441000 1210991 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": 762270, "vin": [ { "gen": { "height": 762260 } } ], "vout": [ { "amount": 1829432441, "target": { "key": "802620e1f61a97e35c4cb0c16132c4d139b4fee9b51b1db738d3fa06b36c7d6f" } } ], "extra": [ 1, 53, 18, 72, 204, 156, 59, 211, 209, 154, 28, 62, 23, 102, 10, 19, 21, 83, 67, 70, 166, 81, 120, 230, 98, 156, 175, 158, 178, 244, 179, 0, 61, 2, 17, 0, 0, 0, 9, 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