Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f37b9b16942d599062b7d4f7d5da5b4b412aac5e7de1e47e756a5159b4dca0c9

Tx prefix hash: d86dcba16939ed51fb405bdcb341573a73b8aa53492720bc8a6f298ed7cfb0d4
Tx public key: dfa200cbde1ca60fee7a956061740712813c81d94a86730bf14634aa605b1967
Timestamp: 1581091491 Timestamp [UCT]: 2020-02-07 16:04:51 Age [y:d:h:m:s]: 05:271:08:01:02
Block: 60718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343687 RingCT/type: yes/0
Extra: 01dfa200cbde1ca60fee7a956061740712813c81d94a86730bf14634aa605b1967021100000002c71d3ff9000000000000000000

1 output(s) for total of 386.204098253000 dcy

stealth address amount amount idx
00: b5a1446fcd38d9195877a14000288f1d45a3c0530ab1bd3a2946c01edbd2a12c 386.204098253000 111779 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": 60728, "vin": [ { "gen": { "height": 60718 } } ], "vout": [ { "amount": 386204098253, "target": { "key": "b5a1446fcd38d9195877a14000288f1d45a3c0530ab1bd3a2946c01edbd2a12c" } } ], "extra": [ 1, 223, 162, 0, 203, 222, 28, 166, 15, 238, 122, 149, 96, 97, 116, 7, 18, 129, 60, 129, 217, 74, 134, 115, 11, 241, 70, 52, 170, 96, 91, 25, 103, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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