Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d5659001b71a49223117e0dc93c478321ef2883533f119652a29d9f7f24f188

Tx prefix hash: 850b3c824090cc2ec8b008e3c269dda17fb45cd23e7032cc556969ba2e0421c3
Tx public key: bfa18dac599b2bbd1e69b5d0b1a096ab839d8fcf095da7699f3c3b8c2b343742
Timestamp: 1734350419 Timestamp [UCT]: 2024-12-16 12:00:19 Age [y:d:h:m:s]: 00:092:22:25:29
Block: 1176439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66201 RingCT/type: yes/0
Extra: 01bfa18dac599b2bbd1e69b5d0b1a096ab839d8fcf095da7699f3c3b8c2b343742021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfcfd13177f8a655430343c52caa2ed9af8e2db53a57e950e6541bed9db245d4 0.600000000000 1662772 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": 1176449, "vin": [ { "gen": { "height": 1176439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfcfd13177f8a655430343c52caa2ed9af8e2db53a57e950e6541bed9db245d4" } } ], "extra": [ 1, 191, 161, 141, 172, 89, 155, 43, 189, 30, 105, 181, 208, 177, 160, 150, 171, 131, 157, 143, 207, 9, 93, 167, 105, 159, 60, 59, 140, 43, 52, 55, 66, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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