Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0307f809c07fddabd018f7d77bcedb5f6faab9810b396600deb9cadc39211607

Tx prefix hash: 0963c90ce84b200a460693b8e37825128f2bea10f81118af9ca6c1e14321c6c4
Tx public key: dd50a6ea9ce67bdc97245330fce480cb12413eba60a9bf3b4ccdacbaad355b9c
Timestamp: 1580568241 Timestamp [UCT]: 2020-02-01 14:44:01 Age [y:d:h:m:s]: 05:036:11:47:27
Block: 56543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177974 RingCT/type: yes/0
Extra: 01dd50a6ea9ce67bdc97245330fce480cb12413eba60a9bf3b4ccdacbaad355b9c021100000004b221b3d1000000000000000000

1 output(s) for total of 398.703815962000 dcy

stealth address amount amount idx
00: 7422ace36b7ff4a67b30c6a7a726ab26e134f178f8a4e5c27b462fa8348fc3ac 398.703815962000 104286 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": 56553, "vin": [ { "gen": { "height": 56543 } } ], "vout": [ { "amount": 398703815962, "target": { "key": "7422ace36b7ff4a67b30c6a7a726ab26e134f178f8a4e5c27b462fa8348fc3ac" } } ], "extra": [ 1, 221, 80, 166, 234, 156, 230, 123, 220, 151, 36, 83, 48, 252, 228, 128, 203, 18, 65, 62, 186, 96, 169, 191, 59, 76, 205, 172, 186, 173, 53, 91, 156, 2, 17, 0, 0, 0, 4, 178, 33, 179, 209, 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