Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33b3e147305d2431141134b52294c2f0c2e2b8f2ab15c7ce862c60d72523e251

Tx prefix hash: 21fd1946d7b99e6ace657181f355ae28a9befc9967fcc6980ac9079b17a5b60a
Tx public key: b4ae65e06cd52cab9e095ad16afc2b96d22ee3663a93ee745136a19075143acc
Timestamp: 1582008132 Timestamp [UCT]: 2020-02-18 06:42:12 Age [y:d:h:m:s]: 05:015:23:43:41
Block: 67274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164490 RingCT/type: yes/0
Extra: 01b4ae65e06cd52cab9e095ad16afc2b96d22ee3663a93ee745136a19075143acc02110000001a4943cd9f000000000000000000

1 output(s) for total of 367.361905366000 dcy

stealth address amount amount idx
00: b9d4b06207aa04e82bc5df53f3d11d53a75ea173faf5175825ab775875d6f67a 367.361905366000 123966 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": 67284, "vin": [ { "gen": { "height": 67274 } } ], "vout": [ { "amount": 367361905366, "target": { "key": "b9d4b06207aa04e82bc5df53f3d11d53a75ea173faf5175825ab775875d6f67a" } } ], "extra": [ 1, 180, 174, 101, 224, 108, 213, 44, 171, 158, 9, 90, 209, 106, 252, 43, 150, 210, 46, 227, 102, 58, 147, 238, 116, 81, 54, 161, 144, 117, 20, 58, 204, 2, 17, 0, 0, 0, 26, 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