Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f3a8d086459745b3a845f27cda4b986ebf1683154314f0bddcdc7d757e21ba0

Tx prefix hash: aa1d2db6829b33a65d9d2b7c31374954bae6c8d817d1bbfe13ed1f5cfc23631b
Tx public key: ee2328eaefaa01b5164ac256b73fbb1983e405f8100852914ddb45dcfc0098f4
Timestamp: 1697140727 Timestamp [UCT]: 2023-10-12 19:58:47 Age [y:d:h:m:s]: 01:089:08:59:35
Block: 868253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325114 RingCT/type: yes/0
Extra: 01ee2328eaefaa01b5164ac256b73fbb1983e405f8100852914ddb45dcfc0098f402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.814924570000 dcy

stealth address amount amount idx
00: 7f3e6030cd22ffd516a81932e23c8d2706bccbad536cfbf9ce8266995932ab38 0.814924570000 1323040 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": 868263, "vin": [ { "gen": { "height": 868253 } } ], "vout": [ { "amount": 814924570, "target": { "key": "7f3e6030cd22ffd516a81932e23c8d2706bccbad536cfbf9ce8266995932ab38" } } ], "extra": [ 1, 238, 35, 40, 234, 239, 170, 1, 181, 22, 74, 194, 86, 183, 63, 187, 25, 131, 228, 5, 248, 16, 8, 82, 145, 77, 219, 69, 220, 252, 0, 152, 244, 2, 17, 0, 0, 0, 1, 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