Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8efdcc2e0005d507edd406336adfeb5114bc504246e34fb072a4e569d2f3cd02

Tx prefix hash: bd442033a226b010ab80bf66d5bf128fdb0e2963796c50981f8070008335ae09
Tx public key: b56ebc720085bcf5d6645fcf0a4608eb5d3fe4a035d0849a3c0107f9b13b9740
Timestamp: 1695945820 Timestamp [UCT]: 2023-09-29 00:03:40 Age [y:d:h:m:s]: 01:148:17:16:32
Block: 858340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367301 RingCT/type: yes/0
Extra: 01b56ebc720085bcf5d6645fcf0a4608eb5d3fe4a035d0849a3c0107f9b13b9740021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.878948260000 dcy

stealth address amount amount idx
00: 9568ec50df536b266124c5ef0b97f7aeb52aa1ff6950113934cd23ba197001c0 0.878948260000 1312510 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": 858350, "vin": [ { "gen": { "height": 858340 } } ], "vout": [ { "amount": 878948260, "target": { "key": "9568ec50df536b266124c5ef0b97f7aeb52aa1ff6950113934cd23ba197001c0" } } ], "extra": [ 1, 181, 110, 188, 114, 0, 133, 188, 245, 214, 100, 95, 207, 10, 70, 8, 235, 93, 63, 228, 160, 53, 208, 132, 154, 60, 1, 7, 249, 177, 59, 151, 64, 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