Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23f960e6e7d2f040d615db82aa681c068727f519315359b08353c37d206e5bcc

Tx prefix hash: bf55bea37d5f7df941503f00b6c665afeff6b1c9deb655b5194c74f2af8e47c2
Tx public key: 680c513d046c1fab1eb9fbc1aca8136ec87d3cb3cd16a8403f8dcaafece6d11d
Timestamp: 1579160007 Timestamp [UCT]: 2020-01-16 07:33:27 Age [y:d:h:m:s]: 04:346:13:03:00
Block: 46653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137168 RingCT/type: yes/0
Extra: 01680c513d046c1fab1eb9fbc1aca8136ec87d3cb3cd16a8403f8dcaafece6d11d0211000000064943cd9f000000000000000000

1 output(s) for total of 429.959527727000 dcy

stealth address amount amount idx
00: e0c574f9bbc239db8bea057d2df2193a1a87abd4da9aa0e1c60b852ceb402101 429.959527727000 85933 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": 46663, "vin": [ { "gen": { "height": 46653 } } ], "vout": [ { "amount": 429959527727, "target": { "key": "e0c574f9bbc239db8bea057d2df2193a1a87abd4da9aa0e1c60b852ceb402101" } } ], "extra": [ 1, 104, 12, 81, 61, 4, 108, 31, 171, 30, 185, 251, 193, 172, 168, 19, 110, 200, 125, 60, 179, 205, 22, 168, 64, 63, 141, 202, 175, 236, 230, 209, 29, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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