Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43345ae5fb513e04d7f905051c62b6966a21ce9e614f975bdab0df2e88de39c1

Tx prefix hash: d063c14b23a52f8548632deb1f5d13de9197bedc5a52fba643b3ba61032ea654
Tx public key: c786e4c62dbad0a6c350d4875bb81b87e0025b626bed041518166d5518d9124c
Timestamp: 1711744995 Timestamp [UCT]: 2024-03-29 20:43:15 Age [y:d:h:m:s]: 01:222:05:00:59
Block: 989134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417471 RingCT/type: yes/0
Extra: 01c786e4c62dbad0a6c350d4875bb81b87e0025b626bed041518166d5518d9124c02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18633718a4f2ecf61482123d3e5abb0e8282379e05f4f2d4947b14f7905c2ae7 0.600000000000 1449429 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": 989144, "vin": [ { "gen": { "height": 989134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18633718a4f2ecf61482123d3e5abb0e8282379e05f4f2d4947b14f7905c2ae7" } } ], "extra": [ 1, 199, 134, 228, 198, 45, 186, 208, 166, 195, 80, 212, 135, 91, 184, 27, 135, 224, 2, 91, 98, 107, 237, 4, 21, 24, 22, 109, 85, 24, 217, 18, 76, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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