Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf12b6c4964a85163234dc34a3b792d02c944b79465cb21665fd68ce5ea47e03

Tx prefix hash: 654d0b5f771e12426fcca0eb2cab984665bf617d0ab41652dcc0ab9d90ab52f4
Tx public key: dc619d37e6216f70e58bcf598f315ca8c562e2c956ae03476ce57acf45ff5694
Timestamp: 1579353316 Timestamp [UCT]: 2020-01-18 13:15:16 Age [y:d:h:m:s]: 05:036:18:54:35
Block: 48388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176257 RingCT/type: yes/0
Extra: 01dc619d37e6216f70e58bcf598f315ca8c562e2c956ae03476ce57acf45ff569402110000000449b77a3d000000000000000000

1 output(s) for total of 424.329012516000 dcy

stealth address amount amount idx
00: 6054877406783603801884987d522f041162fe40e6bd0d901a2acdaf1c423bda 424.329012516000 89575 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": 48398, "vin": [ { "gen": { "height": 48388 } } ], "vout": [ { "amount": 424329012516, "target": { "key": "6054877406783603801884987d522f041162fe40e6bd0d901a2acdaf1c423bda" } } ], "extra": [ 1, 220, 97, 157, 55, 230, 33, 111, 112, 229, 139, 207, 89, 143, 49, 92, 168, 197, 98, 226, 201, 86, 174, 3, 71, 108, 229, 122, 207, 69, 255, 86, 148, 2, 17, 0, 0, 0, 4, 73, 183, 122, 61, 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