Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355b827b8357ebceb35e276349de0d32cc02c393dd9cf2085b0cb33e326dc78e

Tx prefix hash: c9e97e79ea3f61b56e60bb7fe40dacd4b957e07cced02eba0fbea0def795fbae
Tx public key: bb70a88e7d2f570dc33eddbd3f292dd6bd607aaaec302cf3d9b4b63129a7eb5a
Timestamp: 1702077140 Timestamp [UCT]: 2023-12-08 23:12:20 Age [y:d:h:m:s]: 01:196:03:42:36
Block: 908958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401198 RingCT/type: yes/0
Extra: 01bb70a88e7d2f570dc33eddbd3f292dd6bd607aaaec302cf3d9b4b63129a7eb5a02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 797903b5b1963c895f39c1e9f2d5e4a0f0b74b210c22fefb6ae2b3d7ea69bc72 0.600000000000 1366021 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": 908968, "vin": [ { "gen": { "height": 908958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "797903b5b1963c895f39c1e9f2d5e4a0f0b74b210c22fefb6ae2b3d7ea69bc72" } } ], "extra": [ 1, 187, 112, 168, 142, 125, 47, 87, 13, 195, 62, 221, 189, 63, 41, 45, 214, 189, 96, 122, 170, 236, 48, 44, 243, 217, 180, 182, 49, 41, 167, 235, 90, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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