Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a421f4c3a7212c535a2593274c3cfa2ba9015fbd1d975a8ce878afc8e9f1650

Tx prefix hash: fc90cfaae6f764cb845b4acd5e9a32286e37155e356fa1a3c394462f60868893
Tx public key: 729f5c1ef98d2b233e957a3699111089939f7d4ead448493360412824a955558
Timestamp: 1709380046 Timestamp [UCT]: 2024-03-02 11:47:26 Age [y:d:h:m:s]: 01:083:23:10:02
Block: 969519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321051 RingCT/type: yes/0
Extra: 01729f5c1ef98d2b233e957a3699111089939f7d4ead448493360412824a9555580211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2a4f36f11481091c47747d02b9e3717d80f52f64da40f49beea86c45c4e6a08 0.600000000000 1429354 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": 969529, "vin": [ { "gen": { "height": 969519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2a4f36f11481091c47747d02b9e3717d80f52f64da40f49beea86c45c4e6a08" } } ], "extra": [ 1, 114, 159, 92, 30, 249, 141, 43, 35, 62, 149, 122, 54, 153, 17, 16, 137, 147, 159, 125, 78, 173, 68, 132, 147, 54, 4, 18, 130, 74, 149, 85, 88, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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