Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8a42c0e63203ab975431acdc48d8cca0d82f9e080296abf6bd957557ca2f482

Tx prefix hash: 181a66749ddc035ccc83bf956f26bc1226be8db457f71262015b63be2e5dec6b
Tx public key: f4c9ed8dcc96eb05cfcb5ec2564ad6dc1d13650b48383327eed9413b8b581618
Timestamp: 1659670534 Timestamp [UCT]: 2022-08-05 03:35:34 Age [y:d:h:m:s]: 02:191:20:40:30
Block: 558979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658307 RingCT/type: yes/0
Extra: 01f4c9ed8dcc96eb05cfcb5ec2564ad6dc1d13650b48383327eed9413b8b581618021100000001aac913b7000000000000000000

1 output(s) for total of 8.627215548000 dcy

stealth address amount amount idx
00: 2a8dfda34224308e3e82f900ddaa3d5439c2ef159765f0a3cfc8d60f3168ac3f 8.627215548000 991087 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": 558989, "vin": [ { "gen": { "height": 558979 } } ], "vout": [ { "amount": 8627215548, "target": { "key": "2a8dfda34224308e3e82f900ddaa3d5439c2ef159765f0a3cfc8d60f3168ac3f" } } ], "extra": [ 1, 244, 201, 237, 141, 204, 150, 235, 5, 207, 203, 94, 194, 86, 74, 214, 220, 29, 19, 101, 11, 72, 56, 51, 39, 238, 217, 65, 59, 139, 88, 22, 24, 2, 17, 0, 0, 0, 1, 170, 201, 19, 183, 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