Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58a63f5fb9da9edf7cf019ff193b1cb6994940703d0c72ebc1db969a11b9abc1

Tx prefix hash: 00b63601c5e1b544b8a9875cf7b140f2fe5db576571d2acf9af335225b46b6ee
Tx public key: 55e33d3fc9b55edc6616845693a703e476b2c64951254adb1f6578598010e51d
Timestamp: 1708163453 Timestamp [UCT]: 2024-02-17 09:50:53 Age [y:d:h:m:s]: 01:123:00:11:30
Block: 959422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348858 RingCT/type: yes/0
Extra: 0155e33d3fc9b55edc6616845693a703e476b2c64951254adb1f6578598010e51d0211000000013f0590f7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c86099bc3374378ee6fbaeb03b32d890c0d5caf5589572d0f33b465d9aa5e3fc 0.600000000000 1418957 of 15

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": 959432, "vin": [ { "gen": { "height": 959422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c86099bc3374378ee6fbaeb03b32d890c0d5caf5589572d0f33b465d9aa5e3fc" } } ], "extra": [ 1, 85, 227, 61, 63, 201, 181, 94, 220, 102, 22, 132, 86, 147, 167, 3, 228, 118, 178, 198, 73, 81, 37, 74, 219, 31, 101, 120, 89, 128, 16, 229, 29, 2, 17, 0, 0, 0, 1, 63, 5, 144, 247, 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