Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74a9308d1984e26508e6aa726fccaead436c52265a59ccc73c92a68395165c14

Tx prefix hash: 6dc68872e7f1c74a37c42dc1ac3e1960be5a08a48ccc0c3e886a0b3e8e5d93f2
Tx public key: 8b19ced1646547060f7d99d1f69f086ae1b61650342ca8b350b58a2b86908c9e
Timestamp: 1712322966 Timestamp [UCT]: 2024-04-05 13:16:06 Age [y:d:h:m:s]: 00:344:10:05:10
Block: 993879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246295 RingCT/type: yes/0
Extra: 018b19ced1646547060f7d99d1f69f086ae1b61650342ca8b350b58a2b86908c9e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be6892eead6685edc05e513ee3f51033e903dc41c3ccac477cf2f281ae1445c9 0.600000000000 1454275 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": 993889, "vin": [ { "gen": { "height": 993879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be6892eead6685edc05e513ee3f51033e903dc41c3ccac477cf2f281ae1445c9" } } ], "extra": [ 1, 139, 25, 206, 209, 100, 101, 71, 6, 15, 125, 153, 209, 246, 159, 8, 106, 225, 182, 22, 80, 52, 44, 168, 179, 80, 181, 138, 43, 134, 144, 140, 158, 2, 17, 0, 0, 0, 1, 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