Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97962120920ad9b821b29f8bd88618a41a86a0c78efe37064f343c64bde3edd

Tx prefix hash: a6081eaf71313a4f47489d4dba9a3c1f8a72ce5283db98c9ddc27b5408cabe50
Tx public key: 7476b392d40e647851c173ba1b4c9eff51d9802b9af844fcca1710a4891b86ab
Timestamp: 1695922101 Timestamp [UCT]: 2023-09-28 17:28:21 Age [y:d:h:m:s]: 01:049:08:56:53
Block: 858136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296533 RingCT/type: yes/0
Extra: 017476b392d40e647851c173ba1b4c9eff51d9802b9af844fcca1710a4891b86ab02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.880317322000 dcy

stealth address amount amount idx
00: 8fbe5b88a0b4107f704e308a89d944d303b099b515a9b347b60f928379367bf6 0.880317322000 1312300 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": 858146, "vin": [ { "gen": { "height": 858136 } } ], "vout": [ { "amount": 880317322, "target": { "key": "8fbe5b88a0b4107f704e308a89d944d303b099b515a9b347b60f928379367bf6" } } ], "extra": [ 1, 116, 118, 179, 146, 212, 14, 100, 120, 81, 193, 115, 186, 27, 76, 158, 255, 81, 217, 128, 43, 154, 248, 68, 252, 202, 23, 16, 164, 137, 27, 134, 171, 2, 17, 0, 0, 0, 3, 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